-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MAVLink message actions #1436
Add MAVLink message actions #1436
Conversation
Sometimes anything is something.
a777c9b
to
0362b51
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still reviewing the code and functionalities, but for now, here are some UI observations:
The form is a little bit crammed and the confirm button color needs more contrast.
Try changing the following:
1- Change the confirm button color to white and the others to white but with 80% opacity.
2- Increase the gap-y to let some breeze flow through the form elements :)
3- I think there is no need to repeat Param2 on the box and Parameter 2 on the bottom. Probably only on the box will be fine.
Also, the title 'Message configuration' should be centered on the dialog.
Any message is accepted as long as it's a valid MAVLink message. For COMMAND_LONG and COMMAND_INT messages, the message fields are pre-defined in the UI. For all other messages, the user should specify the JSON message config manually.
0362b51
to
47eaa28
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice feature!
Any message is accepted as long as it's a valid MAVLink message.
For
COMMAND_LONG
andCOMMAND_INT
messages, the message fields are pre-defined in the UI. For all other messages, the user should specify the JSON message config manually.I intend to do a proper automatic parser for all messages soon.
Fix #825
Fix #826